Added Resource google_compute_global_vm_extension_policy#18013
Conversation
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @malhotrasagar2212, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
google_compute_global_vm_extension_policy
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 64ce654: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_global_vm_extension_policy" "primary" {
rollout_operation {
rollout_input {
conflict_behavior = # value needed
name = # value needed
retry_uuid = # value needed
}
rollout_status {
current_rollouts {
location_rollout_status {
location_name = # value needed
}
}
previous_rollout {
location_rollout_status {
location_name = # value needed
}
}
}
}
}
Missing service labelsThe following new resources do not have corresponding service labels:
If you believe this detection to be incorrect please raise the concern with your reviewer. Googlers: This error is safe to ignore once you've completed go/fix-missing-service-labels. Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
🟢 All tests passed! View the recording VCR build log or the debug logs folder for detailed results. @XuechunHou, @malhotrasagar2212 VCR tests complete for 64ce654! |
|
@malhotrasagar2212 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
malhotrasagar2212
left a comment
There was a problem hiding this comment.
Please check the missing test report and add coverage.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 11e4006: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_global_vm_extension_policy" "primary" {
rollout_operation {
rollout_input {
name = # value needed
}
rollout_status {
current_rollouts {
location_rollout_status {
location_name = # value needed
}
}
previous_rollout {
location_rollout_status {
location_name = # value needed
}
}
}
}
}
Missing service labelsThe following new resources do not have corresponding service labels:
If you believe this detection to be incorrect please raise the concern with your reviewer. Googlers: This error is safe to ignore once you've completed go/fix-missing-service-labels. Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
🟢 All tests passed! View the recording VCR build log or the debug logs folder for detailed results. @XuechunHou, @malhotrasagar2212 VCR tests complete for 11e4006! |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 32737bc: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_global_vm_extension_policy" "primary" {
rollout_operation {
rollout_input {
name = # value needed
}
rollout_status {
current_rollouts {
location_rollout_status {
location_name = # value needed
}
}
previous_rollout {
location_rollout_status {
location_name = # value needed
}
}
}
}
}
Missing service labelsThe following new resources do not have corresponding service labels:
If you believe this detection to be incorrect please raise the concern with your reviewer. Googlers: This error is safe to ignore once you've completed go/fix-missing-service-labels. Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @XuechunHou, @malhotrasagar2212 VCR tests complete for 32737bc! |
- Add custom POST delete endpoint with required rollout input body. - Split VME Policy tests into Basic and Rollout scenarios.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 61f385b: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_global_vm_extension_policy" "primary" {
rollout_operation {
rollout_input {
name = # value needed
}
rollout_status {
current_rollouts {
location_rollout_status {
location_name = # value needed
}
}
previous_rollout {
location_rollout_status {
location_name = # value needed
}
}
}
}
}
Missing service labelsThe following new resources do not have corresponding service labels:
If you believe this detection to be incorrect please raise the concern with your reviewer. Googlers: This error is safe to ignore once you've completed go/fix-missing-service-labels. Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
🟢 All tests passed! View the recording VCR build log or the debug logs folder for detailed results. @XuechunHou, @malhotrasagar2212 VCR tests complete for 61f385b! |
I have updated the tests to include coverage for rollout_input. For the name field, we are currently blocked by an upstream error from the VME team, but I will add that test case as soon as the issue is resolved. Regarding rollout_status, this is a computed-only field generated by the API. As it is not a user-configurable input in Terraform, it has been intentionally omitted from the HCL configuration in the test. |
|
@malhotrasagar2212 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
| # limitations under the License. | ||
|
|
||
| --- | ||
| name: 'GlobalVmExtensionPolicy' |
There was a problem hiding this comment.
Could you please confirm the launch stage/provider target for this resource?
The API reference appears to expose a v1 path, but the 'VM Extension Policy` user-facing docs and gcloud examples still use beta/preview flows. If this is still Pre-GA, then this should be changes to beta-only. If not its fine.
There was a problem hiding this comment.
The API is currently in beta, but is planned to release to GA in July/August. I updated the YAML to align with beta, but we will likely have to change this in the near future.
| // Skip destroy check to avoid eventual consistency issues of global rollouts. | ||
| // The global VM extension policy deletion triggers a background purge rollout | ||
| // that can take a few minutes to fully propagate across GCE zones. | ||
| return nil |
There was a problem hiding this comment.
This destroy check currently returns nil unconditionally. Could we either poll/read until the policy is actually gone, or add a short explanation why a real destroy check is not feasible for the API?
There was a problem hiding this comment.
I updated this in my newest commit to keep polling while we are getting a resource via GET, and when we get a 404 to return success. Let me know what you think.
…the YAML configuration with the beta version.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 7b10347: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_global_vm_extension_policy" "primary" {
rollout_operation {
rollout_input {
name = # value needed
}
rollout_status {
current_rollouts {
location_rollout_status {
location_name = # value needed
}
}
previous_rollout {
location_rollout_status {
location_name = # value needed
}
}
}
}
}
Missing service labelsThe following new resources do not have corresponding service labels:
If you believe this detection to be incorrect please raise the concern with your reviewer. Googlers: This error is safe to ignore once you've completed go/fix-missing-service-labels. Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @XuechunHou, @malhotrasagar2212 VCR tests complete for 7b10347! |
|
@malhotrasagar2212 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
@GoogleCloudPlatform/terraform-team @malhotrasagar2212 This PR has been waiting for review for 1 week. Please take a look! Use the label |
malhotrasagar2212
left a comment
There was a problem hiding this comment.
The `TestAccComputeGlobalVmExtensionPolicy_computeGlobalVmExtensionPolicyRolloutExample' is currently failing and from the logs it looks like the update operation is returning 503 internal error. Has this been confirmed with the VME/API team as an upstream issue?
There was an upstream error related to custom rollout creations which was needed for a test. I am currently fixing that and will commit the fix soon. |
- Support rollout_operation in schema and add custom rollout example - Add post_delete hook to purge all rollout records tied to the VME policy on deletion - Fixes RolloutPlan deletion failures caused by leftover rollout references
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit c7eaa3f: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_global_vm_extension_policy" "primary" {
rollout_operation {
rollout_status {
current_rollouts {
location_rollout_status {
location_name = # value needed
}
}
previous_rollout {
location_rollout_status {
location_name = # value needed
}
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
🟢 All tests passed! View the recording VCR build log or the debug logs folder for detailed results. @XuechunHou, @malhotrasagar2212 VCR tests complete for c7eaa3f! |
|
@malhotrasagar2212 The remaining fields are not inputs to the resource, so those can be safely ignored. We have also submitted the CL for maintainer here: cl/935008647. This new commit should have everything needed for the global policy resource within it! |
malhotrasagar2212
left a comment
There was a problem hiding this comment.
LGTM, thanks!
b29e0ff
Fixes hashicorp/terraform-provider-google#27928
This PR adds support for the new google_compute_global_vm_extension_policy resource to the Google Terraform provider.
Global VM Extension Policies allow you to manage Google software on a fleet of GCE VMs across all zones in a GCP project. Management includes fleetwide installation/uninstallation, configuration management, health reporting, and version upgrades.
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.